…action-cc-connect

# Conflicts:
#	electron/services/providers-api.ts
#	package.json
#	pnpm-lock.yaml

Add operation-level runtime capabilities so cc-connect can report native, proxy, and unsupported sub-operations without overstating OpenClaw parity.

Keep OpenClaw as the default runtime, surface cc-connect operation gaps in Settings, and extend OAuth/bundle E2E coverage plus harness specs for replacement-readiness validation.

Send GUI chat through the Codex bridge so cc-connect runtime sessions use Codex as the execution engine.

Persist Codex JSONL tool call and tool output events as ClawX history messages so the chat execution graph can show command/tool relationships.

Default cc-connect Codex execution to ClawX-managed runtime workspaces under userData instead of the ClawX source checkout.

Map OpenClaw agent ids to cc-connect managed workspace directories without inheriting OpenClaw workspace paths, while preserving explicit workDir overrides for diagnostics.

Keep GitHub and OSS publication tag-only while allowing unsigned workflow-dispatch builds to exercise all five packaged runtime smoke targets.

Pass archive paths directly to tar so Windows runner paths are not shell-escaped. Keep macOS signature verification mandatory by default while allowing explicit unsigned manual smoke evidence.

Keep OAuth acquisition runtime-neutral, synchronize the resulting account through the selected RuntimeProvider, and avoid restarting OpenClaw while cc-connect is active. Preserve the existing OpenClaw projection fallback and surface runtime projection failures to the OAuth flow.

Give newly acquired browser OAuth credentials one-time precedence when syncing cc-connect, while keeping ordinary runtime starts managed-first so Codex token rotation is preserved. Add Electron runtime recovery coverage and machine-readable verifier evidence.

Treat undeclared operations as unsupported after runtime status publishes its operation map, and stop cc-connect-only channel gaps before RPC. Add replacement-required unit and real-bundle verifier evidence.

Route real image, file, audio, and video packets from bundled cc-connect through managed history and GUI Chat. Preserve distinct same-run events, keep runtime media visible beside execution graphs, and add real CLI evidence plus verifier coverage.

Render initial text previews, route handle-only updates across concurrent agents, and clear transient text without discarding structured tool state.\n\nAdd real bundled cc-connect preview/update GUI evidence and keep unsupported upstream delete/button triggers explicit in the validation matrix.

Map public Bridge cards and select options into validated runtime interactions, then return responses through card_action without bypassing cc-connect. Add real bundled Electron evidence for the /lang choice loop and document the v1.4.1 persistence boundary.

Exercise real cc-connect exec and Codex OAuth prompt jobs on native scheduler ticks. Record sanitized UI and machine evidence, preserve runtime PID, and require successful deletion plus post-delete absence.

Mask managed workspace paths in real OAuth screenshots and replace repository, home, and temp roots before persisting local-real reports. Preserve approval, tool lifecycle, generated-file, and retry evidence.

Map the pinned runtime's last_run and last_error fields into the shared Cron contract instead of treating trigger acknowledgement as completion. Make the real OAuth Cron scenario wait for runtime completion before asserting public history and attach bounded diagnostics on failure.

Keep Run Now acknowledgement non-blocking while observing the runtime-owned job until its last run changes or a bounded cancellation condition occurs. Cover delayed success and failure in deterministic Electron tests and the real cc-connect OAuth GUI flow.

Launch Electron with isolated legacy and shared roots to verify startup migration, directory ownership, source retention, and canonical-state precedence across relaunches. Keep the existing flat E2E userData override as the default for all other tests.

Verify real cc-connect channel import keeps OpenClaw compatibility data read-only, stores secrets only in the encrypted vault, and emits sanitized ownership evidence.